Installation as Service for Linux

Install Orchestra Solution Hub as a Linux Service

To install Orchestra Solution Hub as a service in Linux, follow these steps:

1. Edit the Service File

Edit the installation path in the file
<installation_dir>/startscripts/UnixService/solutionhub.service.

If the installation path is /opt/solutionhub, then the changes are:

Environment=ORC_HOME=/opt/solutionhub
ExecStart=/opt/solutionhub/startscripts/UnixService/service_runner.sh

The default Java Development Kit is used from the $JAVA_HOME system variable.
If you wish to use another Java Development Kit, please adjust the variable ORC_JAVA_HOME in file
service_runner.sh.

2. Set Permissions

Run:

sudo chown -R $USER:$GROUPS <installation_dir>
sudo chmod u+x <installation_dir>/startscripts/UnixService/service_runner.sh

3. Copy Service File

Copy
<installation_dir>/startscripts/UnixService/solutionhub.service
to
/etc/systemd/system.

4. Enable and Reload Service

Run:

sudo systemctl enable solutionhub.service
sudo systemctl daemon-reload

5. Update Logging Properties

Edit:

sudo vi ~<installation_dir>/base/classes/logging.properties

Change log file location from relative to absolute path:

• Relative path:
  java.util.logging.FileHandler.pattern = ../../logs/solution_hub_%g.mlog
• Absolute path:
  java.util.logging.FileHandler.pattern = <installation_dir>/logs/solution_hub_%g.mlog

6. Start and Check Service

Run:

sudo systemctl start solutionhub
sudo systemctl status solutionhub

7. Set Permissions on License Store

Run:

sudo chown -R $USER:$GROUPS /opt/orchestraartifact/base/licensestore

8. (Optional) Create Non-Login User

Command	Description
sudo adduser -M solutionhub	Create a new non-login user solutionhub
sudo usermod -aG sudo solutionhub	Add user solutionhub to group sudo

Edit the service to run as this user:

sudo vi /etc/systemd/system/solutionhub.service

Change:

#User=$USER → User=solutionhub
#Group=$GROUPS → Group=orchestra

Then:

sudo systemctl daemon-reload
sudo systemctl restart solutionhub
sudo systemctl status solutionhub

Orchestra Solution Hub should now be running.

9. Test Service

Open your browser and test the default user interface URL:

https://localhost:8453/solution-hub/

---

Configuration of Derby Logging

Logging from the Derby database can be customized by editing:

<installation_dir>/startscripts/UnixService/derby.properties

Since Orchestra Solution Hub is installed as a service, pass the home path of Derby by editing:

startscripts/UnixService/orchestra.sh

and adding the Java argument:

-Dderby.system.home=<installation_dir>/startscripts/UnixService

---

Derby Logging Properties

Name	Default	Description
derby.stream.error.style	rollingFile	If set to rollingFile, Derby creates up to 10 rolling log files named derby-0.log through derby-9.log, each max 1,024,000 bytes.
derby.stream.error.rollingFile.limit	8,388,608 Bytes	Max bytes per rolling log file before rollover (if style is rollingFile).
derby.stream.error.rollingFile.count	10	Number of rolling log files before deleting the oldest (if style is rollingFile).

---

info

• For changes to take effect, restart Orchestra Solution Hub.
• You can restore default Derby settings by removing the derby.properties file.
• Additional parameters are documented in the Derby documentation.